Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1583

reference
489-tree-1
name
1583
tree-preservation-order

undefined

489-tpo-1
uprn
address-text
point
POINT (-1.044311 50.894657)
geometry
MULTIPOLYGON (((-1.044254 50.894651,-1.044257 50.894663,-1.044265 50.894673,-1.044277 50.894681,-1.044293 50.894686,-1.044311 50.894688,-1.044328 50.894686,-1.044344 50.894681,-1.044357 50.894673,-1.044365 50.894663,-1.044368 50.894652,-1.044366 50.894641,-1.044358 50.894631,-1.044345 50.894623,-1.044330 50.894618,-1.044312 50.894616,-1.044294 50.894618,-1.044279 50.894623,-1.044266 50.894630,-1.044258 50.894640,-1.044254 50.894651)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL